-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix jest-haste-map on vagrant. #984
Conversation
@facebook-github-bot import |
Thanks for importing. If you are an FB employee go to Phabricator to review. |
Any chance this is the same fix needed to make coverage and runInBand work together? |
Probably not, looks like a different bug unfortunately :( |
We really need to start using flow + add more integration tests. |
8797ecb
I think the proper fix should be around here (assuming that options.maxWorkers should represent the number of cores) In the highlighted lines the |
I can confirm this PR fixes my issue. |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This is a similar fix to what @spicyj did in sophiebits@cff1410 a long time ago. I wasn't aware of why we had this but it seems obvious to me that we shouldn't create processes if there are less than one worker available. Not really sure how that could happen but it seems that on vagrant/docker installs the number of cores is 0.
See #980.